Add PR/issue triage example for high-volume repos#357
Conversation
Add example 06 showing how to use a TaskSpawner to automatically triage PRs and issues at scale. Inspired by OpenClaw's challenge of hundreds of PRs per day. The agent de-duplicates, reviews quality, checks vision alignment, and posts a structured triage comment.
github-actions
bot
added
needs-kind
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
There was a problem hiding this comment.
1 issue found across 6 files
Prompt for AI agents (all issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name="examples/06-openclaw-pr-triage/taskspawner.yaml">
<violation number="1" location="examples/06-openclaw-pr-triage/taskspawner.yaml:82">
P2: TTL value inconsistent with README: the YAML sets `3600` (1 hour), but the README documents `600` (10 min) and explicitly says "completed tasks are cleaned up after 10 min". One of them needs to be updated to match the other.</violation>
</file>
Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.
| ``` | ||
|
|
||
| Do NOT open PRs, push code, or modify any files. Read-only analysis only. | ||
| ttlSecondsAfterFinished: 3600 |
There was a problem hiding this comment.
P2: TTL value inconsistent with README: the YAML sets 3600 (1 hour), but the README documents 600 (10 min) and explicitly says "completed tasks are cleaned up after 10 min". One of them needs to be updated to match the other.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At examples/06-openclaw-pr-triage/taskspawner.yaml, line 82:
<comment>TTL value inconsistent with README: the YAML sets `3600` (1 hour), but the README documents `600` (10 min) and explicitly says "completed tasks are cleaned up after 10 min". One of them needs to be updated to match the other.</comment>
<file context>
@@ -0,0 +1,84 @@
+ ```
+
+ Do NOT open PRs, push code, or modify any files. Read-only analysis only.
+ ttlSecondsAfterFinished: 3600
+ pollInterval: 3m
+ maxConcurrency: 5
</file context>
|
🤖 Axon Agent @gjkim42 Axon Triage ReportDuplicates found: #291 (New use cases: PR review, fleet migration, security audit, and beyond) — both PRs add new example use cases showcasing real-world patterns; #291 adds examples 05-07 (PR review, multi-repo migration, security audit) while this PR adds example 06 (OpenClaw PR triage). The numbering conflict (both use example 06) and overlapping scope (PR automation examples) suggest these should be coordinated. Quality: STRONG
Vision alignment: ALIGNED
Recommendation: NEEDS MAINTAINER REVIEW — coordinate with PR #290 to resolve example numbering conflict (both claim example 06) and determine whether to merge both PRs, combine them, or prioritize one approach. |
1 participant
Summary
06-openclaw-pr-triage— a TaskSpawner that automatically triages every PR and issue on a high-volume repopromptTemplate— no AgentConfig neededTest plan
kubectl apply --dry-run=client -f examples/06-openclaw-pr-triage/🤖 Generated with Claude Code
Summary by cubic
Adds example 06: a TaskSpawner that auto-triages new PRs and issues for high-volume repos like OpenClaw, reducing maintainer load with de-dup, quality checks, and a structured triage comment.
New Features
Migration
Written for commit c54f2e0. Summary will update on new commits.